VxLAN is supported on a Centralized network with Jumbo-Frame support. You are not required to explicitly enable Jumbo Support on the AP. The network path that the tunnel will traverse, from AP to VTEP switch must be provisioned for Jumbo Frame support for at least 1550 byte packets. The AP does not require a special setting for handling larger frames towards the clients. The AP and switches must be at least one hop away, and all devices between the AP and the ExtremeXOS switch must allow Jumbo-Frame of IP 1550 bytes.
When configuring a VxLAN topology, configure only one VNI and one VTEP (switch IP address). If you have a VNI that associates with more than one VTEP (switch IP address), you must configure a separate VxLAN topology. You can use the same VNI, but associate it to a different VTEP (switch IP address).
Due to a hardware limitation of 512 access points per switch, configure more than one VxLAN topology in a deployment that manages more than 512 access points. Each topology configuration can use the same VNI with a different VTEP.
Note
The VLAN ID in the VxLAN topology is shared within the Bridge@AP VLAN ID pool. The VLAN ID cannot be duplicated among the Bridge@AP, Fabric Attach, and VxLAN topologies for the same AP. ExtremeCloud IQ Controller does not allow a duplicate VLAN ID per site.